🚀 Preview deployment: https://layer5.io/pr-preview/pr-7843/

Note: Preview may take a moment (GitHub Pages deployment in progress). Please wait and refresh. Track deployment here

@ananyaa0518 Thank you for your contribution! Let's discuss this during the website call tomorrow at 5:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂

@Oluwatunmise-olat Thanks for the feedback! I've updated the button styling to ensure all three actions have consistent sizing while preserving the existing column layout. The latest changes have been pushed and the updated preview/screenshots are available for review.

Is there any reason why the nav bar is duplicated?

Thanks for catching that! The duplicated navbar is only appearing in my local environment and doesn't show up in the deployed preview.

@KhushamBansal Thanks for bringing that up! I can think of two possible approaches here:

• Only render the "Report Broken Link" action when document.referrer is present, which would avoid reports from manually entered URLs while still capturing broken links from search engines, external sites, and internal navigation.

• Keep the reporting action available, but if document.referrer is empty, show a confirmation dialog reminding users to verify that they didn't manually enter the URL before submitting a report.

Which approach would you prefer, or do you have another approach in mind?

@ananyaa0518 I would prefer 2nd approach.

@Oluwatunmise-olat @KhushamBansal Great, thanks for the clarification! I'll implement the second approach and update the PR.

I've updated the implementation to address this case. Now, if document.referrer is empty, users are shown a confirmation dialog reminding them to verify that they didn't manually enter the URL before proceeding with the broken link report. If they confirm, the existing reporting flow continues as before. I've also updated the demo/screenshots in the PR. Please take a look when you have a chance.